vendor._lattice: OFS1P3DX -> OFD1P3DX and IFS1P3DX -> IFD1P3DX for nexus #1346
+58
−7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lattice renamed some IO primitives when moving from Diamond to Radiant. This is, naturally, sparsely documented but I found a reference in Table 41 of 1. One letter in the name of each primitives is changed, as well as one of the inputs (
i_SCLK
->i_CK
). This requires a different IO Buffer specialisation for Nexus (Radiant) compared to MachXO2 and ECP5 which this PR adds.I don't quite know which name Oxide would expect, but a quick grep among the fuzzing scripts finds the updated name (same as Radiant) and not the previous one. So I assume this change is applicable to Oxide also.
Support for Nexus was recently added in #1342
Footnotes
https://www.latticesemi.com/-/media/LatticeSemi/Documents/UserManuals/RZ2/Radiant2_1_migration_guide_diamond.ashx?document_id=52926 ↩